PageSpeed Insights logo
PageSpeed Insights
PageSpeed Insights
This site uses cookies from Google to deliver its services and to analyze traffic.
Report from Sep 28, 2025, 11:18:09 PM
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
3.5 s
Page LoadsGood (≤ 2.5 s)56%Needs Improvement (2.5 s - 4 s)24%Poor (> 4 s)19%75th Percentile - 3.5 sCore Web Vital
Interaction to Next Paint (INP)
322 ms
Page LoadsGood (≤ 200 ms)52%Needs Improvement (200 ms - 500 ms)36%Poor (> 500 ms)12%75th Percentile - 322 msCore Web Vital
Cumulative Layout Shift (CLS)
0.1
Page LoadsGood (≤ 0.1)74%Needs Improvement (0.1 - 0.25)7%Poor (> 0.25)18%75th Percentile - 0.1Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2 s
Page LoadsGood (≤ 1.8 s)69%Needs Improvement (1.8 s - 3 s)19%Poor (> 3 s)12%75th Percentile - 2 s 
Time to First Byte (TTFB)
0.8 s
Page LoadsGood (≤ 0.8 s)76%Needs Improvement (0.8 s - 1.8 s)17%Poor (> 1.8 s)7%75th Percentile - 0.8 sExperimental
Latest 28-day period
(history)Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
3.3 s
Page LoadsGood (≤ 2.5 s)61%Needs Improvement (2.5 s - 4 s)23%Poor (> 4 s)16%75th Percentile - 3.3 sCore Web Vital
Interaction to Next Paint (INP)
294 ms
Page LoadsGood (≤ 200 ms)59%Needs Improvement (200 ms - 500 ms)31%Poor (> 500 ms)10%75th Percentile - 294 msCore Web Vital
Cumulative Layout Shift (CLS)
0.1
Page LoadsGood (≤ 0.1)74%Needs Improvement (0.1 - 0.25)6%Poor (> 0.25)20%75th Percentile - 0.1Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
2 s
Page LoadsGood (≤ 1.8 s)70%Needs Improvement (1.8 s - 3 s)18%Poor (> 3 s)12%75th Percentile - 2 s 
Time to First Byte (TTFB)
0.8 s
Page LoadsGood (≤ 0.8 s)76%Needs Improvement (0.8 s - 1.8 s)17%Poor (> 1.8 s)7%75th Percentile - 0.8 sExperimental
Latest 28-day period
(history)Various mobile devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
45
Performance
93
Accessibility
79
Best Practices
75
SEO
45
Performance
93
Accessibility
79
Best Practices
75
SEO
45 FCP+2LCP+0TBT+15CLS+25SI+3 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
4.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
13.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
600 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
6.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Sep 28, 2025, 11:18 PM GMT+6
  • Emulated Moto G Power with Lighthouse 12.8.2
    Unthrottled CPU/Memory Power: 649 CPU throttling: 1.2x slowdown (Simulated) Screen emulation: 412x823, DPR 1.75 Axe version: 4.10.3
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Slow 4G throttling
    Network throttling: 150 ms TCP RTT, 1,638.4 kb/s throughput (Simulated) Browser location: Asia
  • Using HeadlessChromium 137.0.7151.119 with lr
    User agent (network): "Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Later this year, insights will replace performance audits. Learn more and provide feedback here.
Show audits relevant to:
Insights
Use efficient cache lifetimes Est savings of 1,803 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.LCPFCP
Request
Cache TTL
Transfer Size
populardiagnostic.com
1st party
2,718 KiB
/assets/4-33a2F2a_.webp
(www.populardiagnostic.com)
4h
501 KiB
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
4h
334 KiB
/assets/5-DVECcc1c.webp
(www.populardiagnostic.com)
4h
225 KiB
/assets/6-CS5LWHS4.webp
(www.populardiagnostic.com)
4h
219 KiB
/assets/3-D5xSDq2G.webp
(www.populardiagnostic.com)
4h
167 KiB
/assets/2-CgtAcksK.webp
(www.populardiagnostic.com)
4h
142 KiB
/assets/link-BH2Tfz_i.webp
(www.populardiagnostic.com)
4h
130 KiB
/assets/11-T1pN_r_p.webp
(www.populardiagnostic.com)
4h
128 KiB
/assets/7-B0IBPWau.webp
(www.populardiagnostic.com)
4h
124 KiB
/assets/12-L24Tbupz.webp
(www.populardiagnostic.com)
4h
107 KiB
/assets/10-fKvuecZo.webp
(www.populardiagnostic.com)
4h
91 KiB
/assets/index-D9TpzPx-.js
(www.populardiagnostic.com)
4h
88 KiB
/assets/9-Bthm9HJc.webp
(www.populardiagnostic.com)
4h
87 KiB
/assets/8-CmjkCUjW.webp
(www.populardiagnostic.com)
4h
83 KiB
/assets/13-Cub4C-YK.webp
(www.populardiagnostic.com)
4h
50 KiB
/assets/14-BkvHjxjg.webp
(www.populardiagnostic.com)
4h
48 KiB
/assets/ubuntu-la….woff2
(www.populardiagnostic.com)
4h
35 KiB
/assets/index-D6li_RNe.css
(www.populardiagnostic.com)
4h
19 KiB
/assets/logo-D2TkWYd3.webp
(www.populardiagnostic.com)
4h
10 KiB
/assets/main-dcfkQSH9.jsx
(www.populardiagnostic.com)
None
6 KiB
/assets/Amarlab-DUWBO2sp.webp
(www.populardiagnostic.com)
4h
6 KiB
/assets/Hajj-A067Mk4w.webp
(www.populardiagnostic.com)
4h
6 KiB
/assets/PureHealt….webp
(www.populardiagnostic.com)
4h
6 KiB
/assets/Arogga-B5qBNRyI.webp
(www.populardiagnostic.com)
4h
5 KiB
/assets/logo1-61ask-p-.webp
(www.populardiagnostic.com)
4h
3 KiB
…partner/14-201….png
(old.populardiagnostic.com)
7d
17 KiB
https://www.populardiagnostic.com
None
2 KiB
…partner/23-201….jpg
(old.populardiagnostic.com)
7d
12 KiB
…partner/51-201….jpg
(old.populardiagnostic.com)
7d
11 KiB
…partner/12-201….jpg
(old.populardiagnostic.com)
7d
9 KiB
…partner/18-201….jpg
(old.populardiagnostic.com)
7d
9 KiB
…partner/180-201….jpg
(old.populardiagnostic.com)
7d
7 KiB
…partner/28-201….jpg
(old.populardiagnostic.com)
7d
6 KiB
…partner/67-201….jpg
(old.populardiagnostic.com)
7d
6 KiB
…partner/123-201….jpg
(old.populardiagnostic.com)
7d
6 KiB
…partner/24-201….jpg
(old.populardiagnostic.com)
7d
6 KiB
…partner/78-201….jpg
(old.populardiagnostic.com)
7d
5 KiB
revechat.com
11 KiB
/images/revechat-logo-v4.svg
(static.revechat.com)
4h
7 KiB
/images/ChatCircleClose.svg
(static.revechat.com)
4h
1 KiB
/images/DeviceMobileOTP.svg
(static.revechat.com)
4h
1 KiB
/images/google.svg
(static.revechat.com)
4h
1 KiB
/images/facebook.svg
(static.revechat.com)
4h
1 KiB
Improve image delivery Est savings of 1,719 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image sizeLCPFCP
URL
Resource Size
Est Savings
populardiagnostic.com
1st party
2,173.4 KiB
1,718.8 KiB
/assets/4-33a2F2a_.webp
(www.populardiagnostic.com)
500.6 KiB
460.4 KiB
Increasing the image compression factor could improve this image's download size.
391.1 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
317.1 KiB
/assets/5-DVECcc1c.webp
(www.populardiagnostic.com)
224.1 KiB
184.0 KiB
Increasing the image compression factor could improve this image's download size.
114.6 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
142.0 KiB
/assets/6-CS5LWHS4.webp
(www.populardiagnostic.com)
218.0 KiB
177.9 KiB
Increasing the image compression factor could improve this image's download size.
108.5 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
138.1 KiB
/assets/link-BH2Tfz_i.webp
(www.populardiagnostic.com)
129.3 KiB
129.1 KiB
This image file is larger than it needs to be (8838x315) for its displayed dimensions (380x14). Use responsive images to reduce the image download size.
129.1 KiB
/assets/3-D5xSDq2G.webp
(www.populardiagnostic.com)
166.3 KiB
126.2 KiB
Increasing the image compression factor could improve this image's download size.
56.8 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
105.3 KiB
/assets/2-CgtAcksK.webp
(www.populardiagnostic.com)
141.3 KiB
101.2 KiB
Increasing the image compression factor could improve this image's download size.
31.8 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
89.5 KiB
/assets/11-T1pN_r_p.webp
(www.populardiagnostic.com)
127.2 KiB
87.1 KiB
Increasing the image compression factor could improve this image's download size.
17.7 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
80.6 KiB
/assets/7-B0IBPWau.webp
(www.populardiagnostic.com)
122.9 KiB
82.7 KiB
Increasing the image compression factor could improve this image's download size.
13.4 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
77.8 KiB
/assets/12-L24Tbupz.webp
(www.populardiagnostic.com)
106.4 KiB
67.4 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
67.4 KiB
/assets/10-fKvuecZo.webp
(www.populardiagnostic.com)
89.8 KiB
56.9 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
56.9 KiB
/assets/9-Bthm9HJc.webp
(www.populardiagnostic.com)
85.9 KiB
54.4 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
54.4 KiB
/assets/8-CmjkCUjW.webp
(www.populardiagnostic.com)
82.0 KiB
51.9 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
51.9 KiB
/assets/13-Cub4C-YK.webp
(www.populardiagnostic.com)
49.6 KiB
31.4 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
31.4 KiB
/assets/14-BkvHjxjg.webp
(www.populardiagnostic.com)
47.6 KiB
30.1 KiB
This image file is larger than it needs to be (961x700) for its displayed dimensions (822x300). Use responsive images to reduce the image download size.
30.1 KiB
…partner/14-201….png
(old.populardiagnostic.com)
16.6 KiB
16.0 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
14.1 KiB
This image file is larger than it needs to be (150x101) for its displayed dimensions (71x48). Use responsive images to reduce the image download size.
12.8 KiB
…partner/23-201….jpg
(old.populardiagnostic.com)
11.7 KiB
11.2 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
9.3 KiB
This image file is larger than it needs to be (150x100) for its displayed dimensions (72x48). Use responsive images to reduce the image download size.
9.0 KiB
…partner/51-201….jpg
(old.populardiagnostic.com)
10.6 KiB
10.1 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
8.2 KiB
This image file is larger than it needs to be (150x100) for its displayed dimensions (72x48). Use responsive images to reduce the image download size.
8.2 KiB
/assets/logo-D2TkWYd3.webp
(www.populardiagnostic.com)
9.6 KiB
9.6 KiB
This image file is larger than it needs to be (634x627) for its displayed dimensions (22x22). Use responsive images to reduce the image download size.
9.6 KiB
…partner/12-201….jpg
(old.populardiagnostic.com)
8.8 KiB
8.2 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
6.4 KiB
This image file is larger than it needs to be (150x100) for its displayed dimensions (72x48). Use responsive images to reduce the image download size.
6.8 KiB
…partner/18-201….jpg
(old.populardiagnostic.com)
8.2 KiB
7.6 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
5.8 KiB
This image file is larger than it needs to be (150x100) for its displayed dimensions (72x48). Use responsive images to reduce the image download size.
6.3 KiB
…partner/180-201….jpg
(old.populardiagnostic.com)
6.5 KiB
5.9 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
4.1 KiB
This image file is larger than it needs to be (150x100) for its displayed dimensions (72x48). Use responsive images to reduce the image download size.
5.0 KiB
…partner/28-201….jpg
(old.populardiagnostic.com)
5.3 KiB
4.8 KiB
This image file is larger than it needs to be (150x100) for its displayed dimensions (72x48). Use responsive images to reduce the image download size.
4.1 KiB
…partner/67-201….jpg
(old.populardiagnostic.com)
5.3 KiB
4.7 KiB
This image file is larger than it needs to be (150x100) for its displayed dimensions (72x48). Use responsive images to reduce the image download size.
4.1 KiB
Render blocking requests Est savings of 450 ms
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.LCPFCP
URL
Transfer Size
Duration
populardiagnostic.com
1st party
19.1 KiB
330 ms
/assets/index-D6li_RNe.css
(www.populardiagnostic.com)
19.1 KiB
330 ms
Google Fonts
cdn
1.4 KiB
480 ms
/css2?family=…
(fonts.googleapis.com)
1.4 KiB
480 ms
Forced reflow
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Top function call
Total reflow time
/assets/index-B8iloa7z.js:62:516248
(www.populardiagnostic.com)
26 ms
Source
Total reflow time
/assets/index-B8iloa7z.js:61:103947
(www.populardiagnostic.com)
11 ms
/assets/index-B8iloa7z.js:61:516207
(www.populardiagnostic.com)
26 ms
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loadingLCP
  • lazy load not applied
  • fetchpriority=high should be applied
  • Request is discoverable in initial document
Healthcare service 2
<img src="/assets/2-CgtAcksK.webp" alt="Healthcare service 2" class="w-full h-full object-cover object-center" loading="eager">
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.LCP
Maximum critical path latency: 1,504 ms
Initial Navigation
https://www.populardiagnostic.com
- 73 ms, 1.70 KiB
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
- 469 ms, 334.16 KiB
/assets/index-D9TpzPx-.js
(www.populardiagnostic.com)
- 786 ms, 88.45 KiB
/api/branch-for-doctor?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,431 ms, 1.35 KiB
/api/doctor-speciality?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,313 ms, 1.66 KiB
/api/practice-days?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,451 ms, 0.89 KiB
/api/partners?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,315 ms, 1.37 KiB
/api/testimonials?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,439 ms, 1.38 KiB
/api/social-links?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 937 ms, 0.96 KiB
/api/social-links?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 939 ms, 0.96 KiB
/assets/index-D6li_RNe.css
(www.populardiagnostic.com)
- 126 ms, 19.08 KiB
/css2?family=…
(fonts.googleapis.com)
- 129 ms, 1.40 KiB
…v24/pxiEyp8kv….woff2
(fonts.gstatic.com)
- 727 ms, 8.51 KiB
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
- 1,141 ms, 8.35 KiB
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
- 726 ms, 8.60 KiB
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
- 727 ms, 8.46 KiB
/assets/ubuntu-la….woff2
(www.populardiagnostic.com)
- 1,504 ms, 34.87 KiB
Preconnected origins
preconnect hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
no origins were preconnected
Preconnect candidates
Add preconnect hints to your most important origins, but try to use no more than 4.
Origin
Est LCP savings
https://api.populardiagnostic.com
300 ms
Legacy JavaScript Est savings of 15 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpilingLCPFCP
URL
Wasted bytes
revechat.com
15.2 KiB
…scripts/new-livechat.js?175…
(static.revechat.com)
15.2 KiB
…scripts/new-livechat.js?175…:1:11099
(static.revechat.com)
Array.prototype.forEach
…scripts/new-livechat.js?175…:1:11560
(static.revechat.com)
Array.prototype.indexOf
…scripts/new-livechat.js?175…:1:11465
(static.revechat.com)
Object.create
…scripts/new-livechat.js?175…:1:11828
(static.revechat.com)
String.prototype.startsWith
…scripts/new-livechat.js?175…:1:11001
(static.revechat.com)
String.prototype.trim
Layout shift culprits
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.CLS
Element
Layout shift score
Total
0.001
Doctors
<button type="button" class="inline-block w-full p-3 shadow-2xl rounded text-gray-900 border-r border-g…">
0.001
Payment Partners
<img src="/assets/link-BH2Tfz_i.webp" alt="Payment Partners" class="max-w-full h-auto" loading="lazy">
Unsized image element
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
Web font
…v21/4iCv6KVjb….woff2
(fonts.gstatic.com)
Web font
LCP breakdown
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.LCP
Subpart
Duration
Time to first byte
0 ms
Resource load delay
970 ms
Resource load duration
50 ms
Element render delay
550 ms
Healthcare service 2
<img src="/assets/2-CgtAcksK.webp" alt="Healthcare service 2" class="w-full h-full object-cover object-center" loading="eager">
3rd parties
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
3rd party
Transfer size
Main thread time
revechat.com
1,414 KiB
1,321 ms
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
673 KiB
852 ms
…library/lottie-player.js
(static.revechat.com)
97 KiB
245 ms
…scripts/new-livechat.js?175…
(static.revechat.com)
5 KiB
85 ms
…jquery/jquery.js
(static.revechat.com)
86 KiB
56 ms
…library/dexie.js
(static.revechat.com)
31 KiB
25 ms
…litepicker/litepicker.js
(static.revechat.com)
16 KiB
20 ms
…library/browser.js
(static.revechat.com)
33 KiB
11 ms
…library/marked.min.js
(static.revechat.com)
12 KiB
9 ms
…gallery/gallery.js?ver=1231324-235…-5632r43-03092025
(static.revechat.com)
3 KiB
8 ms
…lightboxed/lightboxed.js?ver=5637-969-6006-57469-03092025
(static.revechat.com)
5 KiB
4 ms
…library/wavesurfer.min.js
(static.revechat.com)
10 KiB
3 ms
…analytics/ga.js?175…
(static.revechat.com)
1 KiB
0 ms
…html/client_version_2.html?ver=250…
(static.revechat.com)
12 KiB
0 ms
…html/media_gallery.html?ver=250…
(static.revechat.com)
2 KiB
0 ms
/images/equilizer.json
(static.revechat.com)
4 KiB
0 ms
…html/client_version_2_banner.html?ver=250…
(static.revechat.com)
1 KiB
0 ms
…sound/cellphone_ring_tone_2.mp3
(static.revechat.com)
136 KiB
0 ms
…css/revechat.min.css?1111-223-03092025
(static.revechat.com)
89 KiB
0 ms
…css/revechat.min.css?535534-5235-2532525-252523-03092025
(static.revechat.com)
44 KiB
0 ms
…phosphor-icons/style-duotone.css
(static.revechat.com)
23 KiB
0 ms
…sound/progressTone.mp3
(static.revechat.com)
17 KiB
0 ms
…phosphor-icons/style-bold.css
(static.revechat.com)
13 KiB
0 ms
…phosphor-icons/style-light.css
(static.revechat.com)
13 KiB
0 ms
…phosphor-icons/style-thin.css
(static.revechat.com)
13 KiB
0 ms
…phosphor-icons/style-normal.css
(static.revechat.com)
13 KiB
0 ms
…phosphor-icons/style-fill.css
(static.revechat.com)
13 KiB
0 ms
…sound/notify.mp3
(static.revechat.com)
11 KiB
0 ms
/images/revechat-logo-v4.svg
(static.revechat.com)
7 KiB
0 ms
…sound/connectTone.mp3
(static.revechat.com)
5 KiB
0 ms
…sound/failTone.mp3
(static.revechat.com)
5 KiB
0 ms
/images/audio-call-avatar.png
(static.revechat.com)
4 KiB
0 ms
…google-fonts-inter/google-fonts.css
(static.revechat.com)
3 KiB
0 ms
…litepicker/litepicker.css
(static.revechat.com)
3 KiB
0 ms
…css/gallery.css?ver=123-123-123-03092025
(static.revechat.com)
2 KiB
0 ms
/images/queue-screen-img.png
(static.revechat.com)
2 KiB
0 ms
…css/jqueryscripttop.css
(static.revechat.com)
1 KiB
0 ms
…css/lightboxed.css?ver=2345235-342-234-2535234-03092025
(static.revechat.com)
1 KiB
0 ms
/images/ChatCircleClose.svg
(static.revechat.com)
1 KiB
0 ms
/images/DeviceMobileOTP.svg
(static.revechat.com)
1 KiB
0 ms
…images/co-browse.png
(static.revechat.com)
1 KiB
0 ms
/images/google.svg
(static.revechat.com)
1 KiB
0 ms
/images/facebook.svg
(static.revechat.com)
1 KiB
0 ms
JSDelivr CDN
cdn
1 KiB
4 ms
…@phosphor-icons/web@2.1.1
(cdn.jsdelivr.net)
1 KiB
4 ms
Google Fonts
cdn
67 KiB
0 ms
…v21/4iCv6KVjb….woff2
(fonts.gstatic.com)
15 KiB
0 ms
…v21/4iCv6KVjb….woff2
(fonts.gstatic.com)
15 KiB
0 ms
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
9 KiB
0 ms
…v24/pxiEyp8kv….woff2
(fonts.gstatic.com)
9 KiB
0 ms
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
8 KiB
0 ms
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
8 KiB
0 ms
/css2?family=Ubuntu:wght@300;400;500;600;700&display=swap
(fonts.googleapis.com)
1 KiB
0 ms
/css2?family=…
(fonts.googleapis.com)
1 KiB
0 ms
Unpkg
cdn
85 KiB
0 ms
…duotone/style.css
(unpkg.com)
23 KiB
0 ms
…regular/style.css
(unpkg.com)
12 KiB
0 ms
…thin/style.css
(unpkg.com)
12 KiB
0 ms
…light/style.css
(unpkg.com)
12 KiB
0 ms
…bold/style.css
(unpkg.com)
12 KiB
0 ms
…fill/style.css
(unpkg.com)
12 KiB
0 ms
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Diagnostics
Reduce JavaScript execution time 2.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
populardiagnostic.com
1st party
3,120 ms
903 ms
137 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
1,991 ms
893 ms
136 ms
https://www.populardiagnostic.com
1,129 ms
10 ms
1 ms
revechat.com
1,584 ms
1,111 ms
394 ms
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
1,067 ms
712 ms
318 ms
…library/lottie-player.js
(static.revechat.com)
306 ms
258 ms
46 ms
…scripts/new-livechat.js?175…
(static.revechat.com)
134 ms
99 ms
3 ms
…jquery/jquery.js
(static.revechat.com)
77 ms
41 ms
27 ms
Unattributable
441 ms
24 ms
0 ms
Unattributable
441 ms
24 ms
0 ms
Minimize main-thread work 5.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
2,096 ms
Other
1,102 ms
Style & Layout
856 ms
Script Parsing & Compilation
605 ms
Rendering
529 ms
Parse HTML & CSS
227 ms
Garbage Collection
22 ms
Reduce unused JavaScript Est savings of 747 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
URL
Transfer Size
Est Savings
revechat.com
849.6 KiB
511.9 KiB
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
638.2 KiB
374.3 KiB
…library/lottie-player.js
(static.revechat.com)
95.6 KiB
61.7 KiB
…jquery/jquery.js
(static.revechat.com)
85.4 KiB
50.3 KiB
…library/dexie.js
(static.revechat.com)
30.3 KiB
25.5 KiB
populardiagnostic.com
1st party
417.4 KiB
234.7 KiB
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
333.2 KiB
160.6 KiB
/assets/index-D9TpzPx-.js
(www.populardiagnostic.com)
84.2 KiB
74.2 KiB
Reduce unused CSS Est savings of 151 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
URL
Transfer Size
Est Savings
Unpkg
cdn
80.1 KiB
80.1 KiB
…duotone/style.css
(unpkg.com)
22.0 KiB
22.0 KiB
…regular/style.css
(unpkg.com)
11.6 KiB
11.6 KiB
…thin/style.css
(unpkg.com)
11.6 KiB
11.6 KiB
…light/style.css
(unpkg.com)
11.6 KiB
11.6 KiB
…fill/style.css
(unpkg.com)
11.6 KiB
11.6 KiB
…bold/style.css
(unpkg.com)
11.6 KiB
11.6 KiB
revechat.com
55.3 KiB
55.3 KiB
…css/revechat.min.css?535534-5235-2532525-252523-03092025
(static.revechat.com)
43.5 KiB
43.5 KiB
…phosphor-icons/style-normal.css
(static.revechat.com)
11.8 KiB
11.8 KiB
populardiagnostic.com
1st party
18.2 KiB
15.3 KiB
/assets/index-D6li_RNe.css
(www.populardiagnostic.com)
18.2 KiB
15.3 KiB
Minify CSS Est savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
URL
Transfer Size
Est Savings
Unpkg
cdn
22.8 KiB
3.3 KiB
…duotone/style.css
(unpkg.com)
22.8 KiB
3.3 KiB
Minify JavaScript Est savings of 40 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
URL
Transfer Size
Est Savings
revechat.com
85.4 KiB
39.9 KiB
…jquery/jquery.js
(static.revechat.com)
85.4 KiB
39.9 KiB
Avoid serving legacy JavaScript to modern browsers Est savings of 23 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpilingLCPFCP
URL
Est Savings
revechat.com
22.6 KiB
…scripts/new-livechat.js?175…
(static.revechat.com)
12.3 KiB
…scripts/new-livechat.js?175…:1:11099
(static.revechat.com)
Array.prototype.forEach
…scripts/new-livechat.js?175…:1:11560
(static.revechat.com)
Array.prototype.indexOf
…scripts/new-livechat.js?175…:1:11465
(static.revechat.com)
Object.create
…scripts/new-livechat.js?175…:1:11828
(static.revechat.com)
String.prototype.startsWith
…scripts/new-livechat.js?175…:1:11001
(static.revechat.com)
String.prototype.trim
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
9.0 KiB
…minify/client.app.min.js?1111-223-03092025:1:2128
(static.revechat.com)
@babel/plugin-transform-spread
…minify/client.app.min.js?1111-223-03092025:1:90920
(static.revechat.com)
Array.prototype.find
…minify/client.app.min.js?1111-223-03092025:1:91268
(static.revechat.com)
Array.prototype.findIndex
…minify/client.app.min.js?1111-223-03092025:1:1531361
(static.revechat.com)
Array.prototype.forEach
…minify/client.app.min.js?1111-223-03092025:1:230105
(static.revechat.com)
Array.prototype.indexOf
…minify/client.app.min.js?1111-223-03092025:1:1531727
(static.revechat.com)
Object.create
…minify/client.app.min.js?1111-223-03092025:1:1532090
(static.revechat.com)
String.prototype.startsWith
…minify/client.app.min.js?1111-223-03092025:1:1531263
(static.revechat.com)
String.prototype.trim
…library/browser.js
(static.revechat.com)
0.7 KiB
…library/browser.js:1:658
(static.revechat.com)
@babel/plugin-transform-classes
…library/browser.js:1:4435
(static.revechat.com)
@babel/plugin-transform-regenerator
…library/browser.js:1:2566
(static.revechat.com)
@babel/plugin-transform-spread
…library/lottie-player.js
(static.revechat.com)
0.5 KiB
…library/lottie-player.js:1:5232
(static.revechat.com)
@babel/plugin-transform-classes
…library/lottie-player.js:1:14500
(static.revechat.com)
@babel/plugin-transform-spread
populardiagnostic.com
1st party
0.7 KiB
/assets/index-D9TpzPx-.js
(www.populardiagnostic.com)
0.5 KiB
/assets/index-D9TpzPx-.js:2:130372
(www.populardiagnostic.com)
@babel/plugin-transform-classes
/assets/index-D9TpzPx-.js:2:79153
(www.populardiagnostic.com)
@babel/plugin-transform-spread
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
0.3 KiB
/assets/index-B8iloa7z.js:67:21502
(www.populardiagnostic.com)
@babel/plugin-transform-spread
Avoid document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Source
revechat.com
…scripts/new-livechat.js?175…:1:6927
(static.revechat.com)
…scripts/new-livechat.js?175…:1:6746
(static.revechat.com)
…scripts/new-livechat.js?175…:1:6612
(static.revechat.com)
Avoid enormous network payloads Total size was 4,296 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
populardiagnostic.com
1st party
1,846.6 KiB
/assets/4-33a2F2a_.webp
(www.populardiagnostic.com)
501.4 KiB
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
334.2 KiB
/assets/5-DVECcc1c.webp
(www.populardiagnostic.com)
224.9 KiB
/assets/6-CS5LWHS4.webp
(www.populardiagnostic.com)
218.8 KiB
/assets/3-D5xSDq2G.webp
(www.populardiagnostic.com)
167.1 KiB
/assets/2-CgtAcksK.webp
(www.populardiagnostic.com)
142.1 KiB
/assets/link-BH2Tfz_i.webp
(www.populardiagnostic.com)
130.1 KiB
/assets/11-T1pN_r_p.webp
(www.populardiagnostic.com)
128.0 KiB
revechat.com
809.8 KiB
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
673.4 KiB
…sound/cellphone_ring_tone_2.mp3
(static.revechat.com)
136.3 KiB
Avoid long main-thread tasks 12 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
revechat.com
1,312 ms
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
14,574 ms
1,031 ms
…scripts/new-livechat.js?175…
(static.revechat.com)
1,511 ms
95 ms
…library/lottie-player.js
(static.revechat.com)
17,004 ms
79 ms
…library/dexie.js
(static.revechat.com)
6,979 ms
55 ms
…jquery/jquery.js
(static.revechat.com)
5,764 ms
52 ms
populardiagnostic.com
1st party
497 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
779 ms
153 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
7,243 ms
95 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
7,338 ms
84 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
7,497 ms
57 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
7,422 ms
54 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
17,108 ms
54 ms
Unattributable
70 ms
Unattributable
932 ms
70 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (10)
Show Hide
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.LCPFCP
  • Avoids redirects
  • Server responds quickly (observed 49 ms)
  • Applies text compression
Optimize DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size.
Statistic
Element
Value
Total elements
638
Most children
Healthcare service 2
<div class="relative h-[300px] sm:h-[400px] md:h-[500px] lg:h-[600px] w-full">
15
DOM depth
div.flex > div.text-[#00984a] > svg.h-6 > path
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="1.5" d="M16 7a4 4 0 11-8 0 4 4 0 018 0zM12 14a7 7 0 00-7 7h14a7 7 0 00-7-7z">
18
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.LCPFCP
Font display
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
INP breakdown
Start investigating with the longest subpart. Delays can be minimized. To reduce processing duration, optimize the main-thread costs, often JS.
Optimize viewport for mobile
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
head > meta
<meta name="viewport" content="width=device-width, initial-scale=1.0">
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
93
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
Appointment
<button type="button" class="inline-block w-full p-3 shadow-2xl rounded text-gray-900 border-r border-g…">
Test Prices
<button type="button" class="inline-block w-full p-3 shadow-2xl rounded text-gray-900 border-r border-g…">
Do you need Emergency Medical Care? Call @ 10636
<h1 class="text-xl sm:text-2xl lg:text-3xl xl:text-4xl font-ubuntu font-bold mb-3 sm:…">
main.relative > section > div.w-full > div.absolute
<div class="absolute w-full h-full top-0 left-0 bg-[#00984a]/70">
main.relative > section > div.w-full > div.w-full
<div class="w-full h-full absolute top-0 left-0 bg-[#00984a]/30">
Doctors Appointment Test Prices Select Branch Select Specialization Select Day …
<div class="bg-[#ffffff]">
or 09666 787801. You can also reach us by the email: info@populardiagnostic.com
<p class="text-sm sm:text-base lg:text-lg font-medium mb-4 sm:mb-6 leading-relaxed m…">
main.relative > section > div.w-full > div.absolute
<div class="absolute w-full h-full top-0 left-0 bg-[#00984a]/70">
main.relative > section > div.w-full > div.w-full
<div class="w-full h-full absolute top-0 left-0 bg-[#00984a]/30">
Doctors Appointment Test Prices Select Branch Select Specialization Select Day …
<div class="bg-[#ffffff]">
Call Now
<a href="tel:10636" class="bg-white text-[#00984a] border rounded px-4 py-3 sm:px-6 sm:py-3 sm:m-2 ho…">
Learn More
<a class="bg-transparent border border-white text-white rounded px-4 py-3 sm:px-6 sm…" href="/hotlines">
main.relative > section > div.w-full > div.absolute
<div class="absolute w-full h-full top-0 left-0 bg-[#00984a]/70">
main.relative > section > div.w-full > div.w-full
<div class="w-full h-full absolute top-0 left-0 bg-[#00984a]/30">
Doctors Appointment Test Prices Select Branch Select Specialization Select Day …
<div class="bg-[#ffffff]">
CONTACT US
<h3 class="text-lg font-bold uppercase tracking-wider">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Head Office (Dhanmondi):
<p class="font-semibold">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
House #16, Road # 2, Dhanmondi R/A, Dhaka-1205, Bangladesh
<p class="py-2">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Phone: 09666 787801, 10636
<p class="mt-4">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
09666 787801
<a href="tel:09666787801" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
10636
<a href="tel:10636" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
View All Branch Hotlines →
<a class="inline-block transition-colors text-sm" href="/hotlines">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
E-mail: info@populardiagnostic.com
<p>
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
info@populardiagnostic.com
<a href="mailto:info@populardiagnostic.com" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
IMPORTANT LINKS
<h3 class="text-lg font-bold uppercase tracking-wider">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Popular Medical College Hospital
<a href="https://www.popular-hospital.com/" target="_blank" rel="noopener noreferrer" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Popular Pharmaceuticals
<a href="https://www.popular-pharma.com/" target="_blank" rel="noopener noreferrer" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Popular Medical College
<a href="https://www.pmch-bd.org/" target="_blank" rel="noopener noreferrer" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
QUICK LINKS
<h3 class="text-lg font-bold uppercase tracking-wider">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Our Branches
<a class="hover:underline" href="/our-branches">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Call for Appointments
<a href="http://appointment.populardiagnostic.com/appointment" target="_blank" rel="noopener noreferrer" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Find Doctors
<a class="hover:underline" href="/our-doctors">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Complain & Advise
<a href="https://complain.populardiagnostic.com/" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
These are opportunities to improve the legibility of your content.
Names and labels
<frame> or <iframe> elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Failing Elements
body > div#reve-chat-container-div > iframe#reve-chat-widget-holder-2
<iframe id="reve-chat-widget-holder-2" src="about:blank" name="reve-chat-widget-holder-2" allow="camera *;microphone *" scrolling="no" style="z-index: 2147483645; min-width: 48px; width: 48px; position: fixed;">
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (25)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (30)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
79
Best Practices
General
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
revechat.com
Unload event listeners are deprecated and will be removed.
…jquery/jquery.js:1083:10
(static.revechat.com)
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
populardiagnostic.com
1st party
/assets/main-dcfkQSH9.jsx:1:0
(www.populardiagnostic.com)
Failed to load module script: Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of "application/x-www-form-urlencoded". Strict MIME type checking is enforced for module scripts per HTML spec.
revechat.com
…minify/client.app.min.js?1111-223-03092025:1:2508641
(static.revechat.com)
WebSocket connection to 'wss://chat-socket.revechat.com/s/W/ws/FJWyekgnrT8tGgAW/M/1759079898820' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
populardiagnostic.com
1st party
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
Large JavaScript file is missing a source map
revechat.com
…library/dexie.js
(static.revechat.com)
…library/dexie.min.js.map
(static.revechat.com)
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
JSDelivr CDN
cdn
…@phosphor-icons/web@2.1.1
(cdn.jsdelivr.net)
/sm/9367c94….map
(cdn.jsdelivr.net)
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
No HSTS header found
High
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Description
Severity
No frame control policy found
High
Mitigate DOM-based XSS with Trusted Types
The require-trusted-types-for directive in the Content-Security-Policy (CSP) header instructs user agents to control the data passed to DOM XSS sink functions. Learn more about mitigating DOM-based XSS with Trusted Types.
Description
Severity
No `Content-Security-Policy` header with Trusted Types directive found
High
Passed audits (12)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids third-party cookies
Third-party cookies may be blocked in some contexts. Learn more about preparing for third-party cookie restrictions.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Source
Selector
% of Page Text
Font Size
Legible text
100.00%
≥ 12px
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (2)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
75
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Content Best Practices
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Link destination
Link Text
populardiagnostic.com
1st party
/hotlines
(www.populardiagnostic.com)
Learn More
Format your HTML in a way that enables crawlers to better understand your app’s content.
Crawling and Indexing
robots.txt is not valid 43 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Line #
Content
Error
1
<!DOCTYPE html>
Syntax not understood
2
<html lang="en">
Syntax not understood
3
  <head>
Syntax not understood
4
    <meta charset="UTF-8" />
Syntax not understood
5
    <link rel="icon" type="image/svg+xml" href="/assets/logo1-61ask-p-.webp" />
Syntax not understood
6
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
Syntax not understood
8
    <!-- Performance optimization meta tags -->
Syntax not understood
9
    <meta name="format-detection" content="telephone=no" />
Syntax not understood
10
    <meta name="theme-color" content="#00984a" />
Syntax not understood
12
    <!-- Preconnect to external domains for faster loading -->
Syntax not understood
13
    <link rel="preconnect" href="https://api.populardiagnostic.com" />
Unknown directive
14
    <link rel="preconnect" href="https://fonts.googleapis.com" />
Unknown directive
15
    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
Unknown directive
16
    <link rel="preconnect" href="https://static.revechat.com" />
Unknown directive
18
    <!-- Preload critical assets -->
Syntax not understood
19
    <link rel="modulepreload" href="/assets/main-dcfkQSH9.jsx" />
Syntax not understood
20
    <link rel="preload" href="/assets/logo-D2TkWYd3.webp" as="image" type="image/webp" />
Syntax not understood
22
    <!-- Font optimization -->
Syntax not understood
23
    <link rel="preload" href="https://fonts.googleapis.com/css2?family=Ubuntu:wght@300;400;500;600;700&display=swap" as="style" />
Unknown directive
24
    <link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Ubuntu:wght@300;400;500;600;700&display=swap" media="print" onload="this.media='all'" />
Unknown directive
26
    <title>Popular Diagnostic Centre Ltd.</title>
Syntax not understood
27
    <script type="module" crossorigin src="/assets/index-B8iloa7z.js"></script>
Syntax not understood
28
    <link rel="stylesheet" crossorigin href="/assets/index-D6li_RNe.css">
Syntax not understood
29
  </head>
Syntax not understood
30
  <body>
Syntax not understood
31
    <div id="root"></div>
Syntax not understood
33
<!-- Start of REVE Chat Script - Deferred for performance -->
Syntax not understood
34
<script type='text/javascript' defer>
Syntax not understood
35
  // Defer chat loading until page is fully loaded
Syntax not understood
36
  window.addEventListener('load', function() {
Syntax not understood
37
    setTimeout(function() {
Syntax not understood
38
      window.$_REVECHAT_API || (function (d, w) {
Syntax not understood
39
        var r = $_REVECHAT_API = function (c) { r._.push(c); }; w.__revechat_account = '6395607'; w.__revechat_version = 2;
Syntax not understood
40
        r._ = []; var rc = d.createElement('script'); rc.type = 'text/javascript'; rc.async = true; rc.setAttribute('charset', 'utf-8');
Syntax not understood
41
        rc.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + 'static.revechat.com' + '/widget/scripts/new-livechat.js?' + new Date().getTime();
Unknown directive
42
        var s = d.getElementsByTagName('script')[0]; s.parentNode.insertBefore(rc, s);
Syntax not understood
43
      })(document, window);
Syntax not understood
44
    }, 2000); // Load chat after 2 seconds
Syntax not understood
45
  });
Syntax not understood
46
</script>
Syntax not understood
47
<!-- End of REVE Chat Script -->
Syntax not understood
48
  </body>
Syntax not understood
49
</html>
Syntax not understood
To appear in search results, crawlers need access to your app.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (6)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Not applicable (1)
Show Hide
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.
Discover what your real users are experiencing
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.9 s
Page LoadsGood (≤ 2.5 s)68%Needs Improvement (2.5 s - 4 s)20%Poor (> 4 s)12%75th Percentile - 2.9 sCore Web Vital
Interaction to Next Paint (INP)
146 ms
Page LoadsGood (≤ 200 ms)83%Needs Improvement (200 ms - 500 ms)11%Poor (> 500 ms)6%75th Percentile - 146 msCore Web Vital
Cumulative Layout Shift (CLS)
0.12
Page LoadsGood (≤ 0.1)74%Needs Improvement (0.1 - 0.25)4%Poor (> 0.25)22%75th Percentile - 0.12Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.5 s
Page LoadsGood (≤ 1.8 s)84%Needs Improvement (1.8 s - 3 s)10%Poor (> 3 s)6%75th Percentile - 1.5 s 
Time to First Byte (TTFB)
1.1 s
Page LoadsGood (≤ 0.8 s)72%Needs Improvement (0.8 s - 1.8 s)23%Poor (> 1.8 s)5%75th Percentile - 1.1 sExperimental
Latest 28-day period
(history)Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Core Web Vitals Assessment: Failed
Largest Contentful Paint (LCP)
2.7 s
Page LoadsGood (≤ 2.5 s)73%Needs Improvement (2.5 s - 4 s)17%Poor (> 4 s)10%75th Percentile - 2.7 sCore Web Vital
Interaction to Next Paint (INP)
125 ms
Page LoadsGood (≤ 200 ms)85%Needs Improvement (200 ms - 500 ms)9%Poor (> 500 ms)5%75th Percentile - 125 msCore Web Vital
Cumulative Layout Shift (CLS)
0.13
Page LoadsGood (≤ 0.1)73%Needs Improvement (0.1 - 0.25)4%Poor (> 0.25)22%75th Percentile - 0.13Core Web Vital
Other Notable Metrics
First Contentful Paint (FCP)
1.5 s
Page LoadsGood (≤ 1.8 s)84%Needs Improvement (1.8 s - 3 s)10%Poor (> 3 s)6%75th Percentile - 1.5 s 
Time to First Byte (TTFB)
0.8 s
Page LoadsGood (≤ 0.8 s)74%Needs Improvement (0.8 s - 1.8 s)22%Poor (> 1.8 s)5%75th Percentile - 0.8 sExperimental
Latest 28-day period
(history)Various desktop devicesMany samples (Chrome UX Report)Full visit durationsVarious network connectionsAll Chrome versions
Diagnose performance issues
50
Performance
89
Accessibility
78
Best Practices
75
SEO
50
Performance
89
Accessibility
78
Best Practices
75
SEO
50 FCP+9LCP+5TBT+10CLS+25SI+2 Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric.
Largest Contentful Paint
3.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time
470 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric.
Cumulative Layout Shift
0.007
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric.
Speed Index
3.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric.
  • Captured at Sep 28, 2025, 11:18 PM GMT+6
  • Emulated Desktop with Lighthouse 12.8.2
    Unthrottled CPU/Memory Power: 658 CPU throttling: 1x slowdown (Simulated) Screen emulation: 1350x940, DPR 1 Axe version: 4.10.3
  • Single page session
    This data is taken from a single page session, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 40 ms TCP RTT, 10,240 kb/s throughput (Simulated) Browser location: Asia
  • Using HeadlessChromium 137.0.7151.119 with lr
    User agent (network): "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36"
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Later this year, insights will replace performance audits. Learn more and provide feedback here.
Show audits relevant to:
Insights
Use efficient cache lifetimes Est savings of 1,803 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.LCPFCP
Request
Cache TTL
Transfer Size
populardiagnostic.com
1st party
2,718 KiB
/assets/4-33a2F2a_.webp
(www.populardiagnostic.com)
4h
501 KiB
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
4h
334 KiB
/assets/5-DVECcc1c.webp
(www.populardiagnostic.com)
4h
225 KiB
/assets/6-CS5LWHS4.webp
(www.populardiagnostic.com)
4h
219 KiB
/assets/3-D5xSDq2G.webp
(www.populardiagnostic.com)
4h
167 KiB
/assets/2-CgtAcksK.webp
(www.populardiagnostic.com)
4h
142 KiB
/assets/link-BH2Tfz_i.webp
(www.populardiagnostic.com)
4h
130 KiB
/assets/11-T1pN_r_p.webp
(www.populardiagnostic.com)
4h
128 KiB
/assets/7-B0IBPWau.webp
(www.populardiagnostic.com)
4h
124 KiB
/assets/12-L24Tbupz.webp
(www.populardiagnostic.com)
4h
107 KiB
/assets/10-fKvuecZo.webp
(www.populardiagnostic.com)
4h
91 KiB
/assets/index-D9TpzPx-.js
(www.populardiagnostic.com)
4h
88 KiB
/assets/9-Bthm9HJc.webp
(www.populardiagnostic.com)
4h
87 KiB
/assets/8-CmjkCUjW.webp
(www.populardiagnostic.com)
4h
83 KiB
/assets/13-Cub4C-YK.webp
(www.populardiagnostic.com)
4h
50 KiB
/assets/14-BkvHjxjg.webp
(www.populardiagnostic.com)
4h
48 KiB
/assets/ubuntu-la….woff2
(www.populardiagnostic.com)
4h
35 KiB
/assets/index-D6li_RNe.css
(www.populardiagnostic.com)
4h
19 KiB
/assets/logo-D2TkWYd3.webp
(www.populardiagnostic.com)
4h
10 KiB
/assets/main-dcfkQSH9.jsx
(www.populardiagnostic.com)
None
6 KiB
/assets/Amarlab-DUWBO2sp.webp
(www.populardiagnostic.com)
4h
6 KiB
/assets/Hajj-A067Mk4w.webp
(www.populardiagnostic.com)
4h
6 KiB
/assets/PureHealt….webp
(www.populardiagnostic.com)
4h
6 KiB
/assets/Arogga-B5qBNRyI.webp
(www.populardiagnostic.com)
4h
5 KiB
/assets/logo1-61ask-p-.webp
(www.populardiagnostic.com)
4h
3 KiB
…partner/14-201….png
(old.populardiagnostic.com)
7d
17 KiB
https://www.populardiagnostic.com
None
2 KiB
…partner/23-201….jpg
(old.populardiagnostic.com)
7d
12 KiB
…partner/51-201….jpg
(old.populardiagnostic.com)
7d
11 KiB
…partner/12-201….jpg
(old.populardiagnostic.com)
7d
9 KiB
…partner/18-201….jpg
(old.populardiagnostic.com)
7d
9 KiB
…partner/180-201….jpg
(old.populardiagnostic.com)
7d
7 KiB
…partner/28-201….jpg
(old.populardiagnostic.com)
7d
6 KiB
…partner/67-201….jpg
(old.populardiagnostic.com)
7d
6 KiB
…partner/24-201….jpg
(old.populardiagnostic.com)
7d
6 KiB
…partner/123-201….jpg
(old.populardiagnostic.com)
7d
6 KiB
…partner/78-201….jpg
(old.populardiagnostic.com)
7d
5 KiB
revechat.com
11 KiB
/images/revechat-logo-v4.svg
(static.revechat.com)
4h
7 KiB
/images/ChatCircleClose.svg
(static.revechat.com)
4h
1 KiB
/images/DeviceMobileOTP.svg
(static.revechat.com)
4h
1 KiB
/images/google.svg
(static.revechat.com)
4h
1 KiB
/images/facebook.svg
(static.revechat.com)
4h
1 KiB
Improve image delivery Est savings of 748 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image sizeLCPFCP
URL
Resource Size
Est Savings
populardiagnostic.com
1st party
2,162.8 KiB
748.4 KiB
/assets/4-33a2F2a_.webp
(www.populardiagnostic.com)
500.6 KiB
340.1 KiB
Increasing the image compression factor could improve this image's download size.
323.1 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
48.0 KiB
/assets/link-BH2Tfz_i.webp
(www.populardiagnostic.com)
129.3 KiB
126.9 KiB
This image file is larger than it needs to be (8838x315) for its displayed dimensions (1216x43). Use responsive images to reduce the image download size.
126.9 KiB
/assets/5-DVECcc1c.webp
(www.populardiagnostic.com)
224.1 KiB
63.6 KiB
Increasing the image compression factor could improve this image's download size.
46.6 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
21.5 KiB
/assets/6-CS5LWHS4.webp
(www.populardiagnostic.com)
218.0 KiB
57.5 KiB
Increasing the image compression factor could improve this image's download size.
40.5 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
20.9 KiB
/assets/3-D5xSDq2G.webp
(www.populardiagnostic.com)
166.3 KiB
15.9 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
15.9 KiB
…partner/14-201….png
(old.populardiagnostic.com)
16.6 KiB
15.0 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
14.1 KiB
This image file is larger than it needs to be (150x101) for its displayed dimensions (119x80). Use responsive images to reduce the image download size.
6.2 KiB
/assets/2-CgtAcksK.webp
(www.populardiagnostic.com)
141.3 KiB
13.5 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
13.5 KiB
/assets/11-T1pN_r_p.webp
(www.populardiagnostic.com)
127.2 KiB
12.2 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
12.2 KiB
/assets/7-B0IBPWau.webp
(www.populardiagnostic.com)
122.9 KiB
11.8 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
11.8 KiB
/assets/12-L24Tbupz.webp
(www.populardiagnostic.com)
106.4 KiB
10.2 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
10.2 KiB
…partner/23-201….jpg
(old.populardiagnostic.com)
11.7 KiB
10.2 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
9.3 KiB
This image file is larger than it needs to be (150x100) for its displayed dimensions (120x80). Use responsive images to reduce the image download size.
4.2 KiB
/assets/logo-D2TkWYd3.webp
(www.populardiagnostic.com)
9.6 KiB
9.6 KiB
This image file is larger than it needs to be (634x627) for its displayed dimensions (22x22). Use responsive images to reduce the image download size.
9.6 KiB
…partner/51-201….jpg
(old.populardiagnostic.com)
10.6 KiB
9.1 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
8.2 KiB
/assets/10-fKvuecZo.webp
(www.populardiagnostic.com)
89.8 KiB
8.6 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
8.6 KiB
/assets/9-Bthm9HJc.webp
(www.populardiagnostic.com)
85.9 KiB
8.2 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
8.2 KiB
/assets/8-CmjkCUjW.webp
(www.populardiagnostic.com)
82.0 KiB
7.9 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
7.9 KiB
…partner/12-201….jpg
(old.populardiagnostic.com)
8.8 KiB
7.2 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
6.4 KiB
…partner/18-201….jpg
(old.populardiagnostic.com)
8.2 KiB
6.6 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
5.8 KiB
…partner/180-201….jpg
(old.populardiagnostic.com)
6.5 KiB
4.9 KiB
Using a modern image format (WebP, AVIF) or increasing the image compression could improve this image's download size.
4.1 KiB
/assets/13-Cub4C-YK.webp
(www.populardiagnostic.com)
49.6 KiB
4.8 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
4.8 KiB
/assets/14-BkvHjxjg.webp
(www.populardiagnostic.com)
47.6 KiB
4.6 KiB
This image file is larger than it needs to be (1558x700) for its displayed dimensions (1643x600). Use responsive images to reduce the image download size.
4.6 KiB
Render blocking requests Est savings of 80 ms
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.LCPFCP
URL
Transfer Size
Duration
populardiagnostic.com
1st party
19.1 KiB
110 ms
/assets/index-D6li_RNe.css
(www.populardiagnostic.com)
19.1 KiB
110 ms
Google Fonts
cdn
1.4 KiB
150 ms
/css2?family=…
(fonts.googleapis.com)
1.4 KiB
150 ms
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loadingLCP
  • lazy load not applied
  • fetchpriority=high should be applied
  • Request is discoverable in initial document
Healthcare service 2
<img src="/assets/2-CgtAcksK.webp" alt="Healthcare service 2" class="w-full h-full object-cover object-center" loading="eager">
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.LCP
Maximum critical path latency: 12,715 ms
Initial Navigation
https://www.populardiagnostic.com
- 277 ms, 1.70 KiB
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
- 515 ms, 334.17 KiB
/api/testimonials?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 12,162 ms, 0.00 KiB
/api/testimonials?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 12,432 ms, 1.38 KiB
/api/testimonials?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 12,715 ms, 1.38 KiB
/assets/index-D9TpzPx-.js
(www.populardiagnostic.com)
- 774 ms, 88.45 KiB
/api/branch-for-doctor?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,384 ms, 1.34 KiB
/api/doctor-speciality?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,343 ms, 1.66 KiB
/api/practice-days?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,480 ms, 0.89 KiB
/api/partners?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,538 ms, 1.37 KiB
/api/testimonials?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 11,061 ms, 0.00 KiB
/api/social-links?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,063 ms, 0.95 KiB
/api/social-links?token=UCbuv3xIy…
(api.populardiagnostic.com)
- 1,078 ms, 0.96 KiB
/assets/index-D6li_RNe.css
(www.populardiagnostic.com)
- 411 ms, 19.08 KiB
/css2?family=…
(fonts.googleapis.com)
- 421 ms, 1.40 KiB
…v24/pxiEyp8kv….woff2
(fonts.gstatic.com)
- 731 ms, 8.51 KiB
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
- 730 ms, 8.35 KiB
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
- 731 ms, 8.60 KiB
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
- 731 ms, 8.46 KiB
/assets/ubuntu-la….woff2
(www.populardiagnostic.com)
- 898 ms, 34.87 KiB
Preconnected origins
preconnect hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
no origins were preconnected
Preconnect candidates
Add preconnect hints to your most important origins, but try to use no more than 4.
No additional origins are good candidates for preconnecting
Legacy JavaScript Est savings of 15 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpilingLCPFCP
URL
Wasted bytes
revechat.com
15.2 KiB
…scripts/new-livechat.js?175…
(static.revechat.com)
15.2 KiB
…scripts/new-livechat.js?175…:1:11099
(static.revechat.com)
Array.prototype.forEach
…scripts/new-livechat.js?175…:1:11560
(static.revechat.com)
Array.prototype.indexOf
…scripts/new-livechat.js?175…:1:11465
(static.revechat.com)
Object.create
…scripts/new-livechat.js?175…:1:11828
(static.revechat.com)
String.prototype.startsWith
…scripts/new-livechat.js?175…:1:11001
(static.revechat.com)
String.prototype.trim
Layout shift culprits
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.CLS
Element
Layout shift score
Total
0.001
Branch Contacts & Help 22+ Branches
<div class="flex items-center gap-3">
0.001
Payment Partners
<img src="/assets/link-BH2Tfz_i.webp" alt="Payment Partners" class="max-w-full h-auto" loading="lazy">
Unsized image element
Branch Contacts & Help 22+ Branches
<div class="flex items-center gap-3">
0.000
Payment Partners
<img src="/assets/link-BH2Tfz_i.webp" alt="Payment Partners" class="max-w-full h-auto" loading="lazy">
Unsized image element
Branch Contacts & Help 22+ Branches
<div class="flex items-center gap-3">
0.000
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
Web font
…v21/4iCv6KVjb….woff2
(fonts.gstatic.com)
Web font
…v21/4iCv6KVjb….woff2
(fonts.gstatic.com)
Web font
…v24/pxiEyp8kv….woff2
(fonts.gstatic.com)
Web font
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
Web font
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
Web font
K+
<span>
0.000
K+
<span>
0.000
Element
Layout shift score
Total
0.007
Smart Actions
<div class="fixed z-30 hidden sm:block right-4" style="top: calc(475px); right: 8px; opacity: 1; transform: none;">
0.007
Element
Layout shift score
Total
0.003
💡 Book an appointment with our specialists Click to visit • Swipe to dismiss 💡 …
<div class="fixed z-30 hidden sm:block right-4" style="top: 195px; right: 8px; opacity: 1; transform: none;">
0.003
LCP breakdown
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.LCP
Subpart
Duration
Time to first byte
0 ms
Resource load delay
910 ms
Resource load duration
30 ms
Element render delay
2,840 ms
Healthcare service 2
<img src="/assets/2-CgtAcksK.webp" alt="Healthcare service 2" class="w-full h-full object-cover object-center" loading="eager">
3rd parties
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
3rd party
Transfer size
Main thread time
revechat.com
1,415 KiB
987 ms
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
674 KiB
496 ms
…library/lottie-player.js
(static.revechat.com)
97 KiB
358 ms
…scripts/new-livechat.js?175…
(static.revechat.com)
5 KiB
39 ms
…jquery/jquery.js
(static.revechat.com)
86 KiB
37 ms
…library/dexie.js
(static.revechat.com)
31 KiB
14 ms
…library/browser.js
(static.revechat.com)
33 KiB
13 ms
…library/marked.min.js
(static.revechat.com)
12 KiB
9 ms
…litepicker/litepicker.js
(static.revechat.com)
16 KiB
8 ms
…gallery/gallery.js?ver=1231324-235…-5632r43-03092025
(static.revechat.com)
3 KiB
6 ms
…library/wavesurfer.min.js
(static.revechat.com)
10 KiB
3 ms
…lightboxed/lightboxed.js?ver=5637-969-6006-57469-03092025
(static.revechat.com)
5 KiB
3 ms
…analytics/ga.js?175…
(static.revechat.com)
1 KiB
1 ms
…html/client_version_2.html?ver=250…
(static.revechat.com)
12 KiB
0 ms
/images/equilizer.json
(static.revechat.com)
4 KiB
0 ms
…html/client_version_2_banner.html?ver=250…
(static.revechat.com)
1 KiB
0 ms
…html/media_gallery.html?ver=250…
(static.revechat.com)
2 KiB
0 ms
…sound/cellphone_ring_tone_2.mp3
(static.revechat.com)
136 KiB
0 ms
…css/revechat.min.css?1111-223-03092025
(static.revechat.com)
89 KiB
0 ms
…css/revechat.min.css?535534-5235-2532525-252523-03092025
(static.revechat.com)
44 KiB
0 ms
…phosphor-icons/style-duotone.css
(static.revechat.com)
23 KiB
0 ms
…sound/progressTone.mp3
(static.revechat.com)
17 KiB
0 ms
…phosphor-icons/style-light.css
(static.revechat.com)
13 KiB
0 ms
…phosphor-icons/style-fill.css
(static.revechat.com)
13 KiB
0 ms
…phosphor-icons/style-bold.css
(static.revechat.com)
13 KiB
0 ms
…phosphor-icons/style-thin.css
(static.revechat.com)
13 KiB
0 ms
…phosphor-icons/style-normal.css
(static.revechat.com)
13 KiB
0 ms
…sound/notify.mp3
(static.revechat.com)
11 KiB
0 ms
/images/revechat-logo-v4.svg
(static.revechat.com)
7 KiB
0 ms
…sound/connectTone.mp3
(static.revechat.com)
5 KiB
0 ms
…sound/failTone.mp3
(static.revechat.com)
5 KiB
0 ms
/images/audio-call-avatar.png
(static.revechat.com)
4 KiB
0 ms
…google-fonts-inter/google-fonts.css
(static.revechat.com)
3 KiB
0 ms
…litepicker/litepicker.css
(static.revechat.com)
3 KiB
0 ms
…css/gallery.css?ver=123-123-123-03092025
(static.revechat.com)
2 KiB
0 ms
/images/queue-screen-img.png
(static.revechat.com)
2 KiB
0 ms
…css/jqueryscripttop.css
(static.revechat.com)
1 KiB
0 ms
…css/lightboxed.css?ver=2345235-342-234-2535234-03092025
(static.revechat.com)
1 KiB
0 ms
/images/ChatCircleClose.svg
(static.revechat.com)
1 KiB
0 ms
/images/DeviceMobileOTP.svg
(static.revechat.com)
1 KiB
0 ms
…images/co-browse.png
(static.revechat.com)
1 KiB
0 ms
/images/google.svg
(static.revechat.com)
1 KiB
0 ms
/images/facebook.svg
(static.revechat.com)
1 KiB
0 ms
JSDelivr CDN
cdn
1 KiB
2 ms
…@phosphor-icons/web@2.1.1
(cdn.jsdelivr.net)
1 KiB
2 ms
Google Fonts
cdn
67 KiB
0 ms
…v21/4iCv6KVjb….woff2
(fonts.gstatic.com)
15 KiB
0 ms
…v21/4iCv6KVjb….woff2
(fonts.gstatic.com)
15 KiB
0 ms
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
9 KiB
0 ms
…v24/pxiEyp8kv….woff2
(fonts.gstatic.com)
9 KiB
0 ms
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
8 KiB
0 ms
…v24/pxiByp8kv….woff2
(fonts.gstatic.com)
8 KiB
0 ms
/css2?family=Ubuntu:wght@300;400;500;600;700&display=swap
(fonts.googleapis.com)
1 KiB
0 ms
/css2?family=…
(fonts.googleapis.com)
1 KiB
0 ms
Unpkg
cdn
85 KiB
0 ms
…duotone/style.css
(unpkg.com)
23 KiB
0 ms
…regular/style.css
(unpkg.com)
12 KiB
0 ms
…light/style.css
(unpkg.com)
12 KiB
0 ms
…bold/style.css
(unpkg.com)
12 KiB
0 ms
…fill/style.css
(unpkg.com)
12 KiB
0 ms
…thin/style.css
(unpkg.com)
12 KiB
0 ms
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Diagnostics
Reduce JavaScript execution time 1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.TBT
URL
Total CPU Time
Script Evaluation
Script Parse
populardiagnostic.com
1st party
3,221 ms
733 ms
85 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
1,998 ms
729 ms
84 ms
https://www.populardiagnostic.com
1,223 ms
4 ms
0 ms
revechat.com
1,031 ms
681 ms
228 ms
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
524 ms
305 ms
197 ms
…library/lottie-player.js
(static.revechat.com)
457 ms
338 ms
30 ms
…scripts/new-livechat.js?175…
(static.revechat.com)
51 ms
38 ms
1 ms
Unattributable
321 ms
12 ms
0 ms
Unattributable
321 ms
12 ms
0 ms
Minimize main-thread work 4.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread workTBT
Category
Time Spent
Script Evaluation
1,476 ms
Other
1,205 ms
Style & Layout
973 ms
Rendering
505 ms
Script Parsing & Compilation
377 ms
Garbage Collection
132 ms
Parse HTML & CSS
114 ms
Reduce unused JavaScript Est savings of 745 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.LCPFCP
URL
Transfer Size
Est Savings
revechat.com
850.0 KiB
512.1 KiB
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
638.6 KiB
374.5 KiB
…library/lottie-player.js
(static.revechat.com)
95.7 KiB
61.8 KiB
…jquery/jquery.js
(static.revechat.com)
85.4 KiB
50.3 KiB
…library/dexie.js
(static.revechat.com)
30.3 KiB
25.5 KiB
populardiagnostic.com
1st party
417.4 KiB
232.7 KiB
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
333.2 KiB
158.5 KiB
/assets/index-D9TpzPx-.js
(www.populardiagnostic.com)
84.2 KiB
74.2 KiB
Minify JavaScript Est savings of 40 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.LCPFCP
URL
Transfer Size
Est Savings
revechat.com
85.4 KiB
39.9 KiB
…jquery/jquery.js
(static.revechat.com)
85.4 KiB
39.9 KiB
Reduce unused CSS Est savings of 150 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.LCPFCP
URL
Transfer Size
Est Savings
Unpkg
cdn
80.1 KiB
80.1 KiB
…duotone/style.css
(unpkg.com)
22.0 KiB
22.0 KiB
…regular/style.css
(unpkg.com)
11.6 KiB
11.6 KiB
…light/style.css
(unpkg.com)
11.6 KiB
11.6 KiB
…bold/style.css
(unpkg.com)
11.6 KiB
11.6 KiB
…fill/style.css
(unpkg.com)
11.6 KiB
11.6 KiB
…thin/style.css
(unpkg.com)
11.6 KiB
11.6 KiB
revechat.com
55.3 KiB
55.3 KiB
…css/revechat.min.css?535534-5235-2532525-252523-03092025
(static.revechat.com)
43.5 KiB
43.5 KiB
…phosphor-icons/style-normal.css
(static.revechat.com)
11.8 KiB
11.8 KiB
populardiagnostic.com
1st party
18.2 KiB
14.3 KiB
/assets/index-D6li_RNe.css
(www.populardiagnostic.com)
18.2 KiB
14.3 KiB
Minify CSS Est savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.LCPFCP
URL
Transfer Size
Est Savings
Unpkg
cdn
22.9 KiB
3.3 KiB
…duotone/style.css
(unpkg.com)
22.9 KiB
3.3 KiB
Avoid serving legacy JavaScript to modern browsers Est savings of 23 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpilingLCPFCP
URL
Est Savings
revechat.com
22.6 KiB
…scripts/new-livechat.js?175…
(static.revechat.com)
12.3 KiB
…scripts/new-livechat.js?175…:1:11099
(static.revechat.com)
Array.prototype.forEach
…scripts/new-livechat.js?175…:1:11560
(static.revechat.com)
Array.prototype.indexOf
…scripts/new-livechat.js?175…:1:11465
(static.revechat.com)
Object.create
…scripts/new-livechat.js?175…:1:11828
(static.revechat.com)
String.prototype.startsWith
…scripts/new-livechat.js?175…:1:11001
(static.revechat.com)
String.prototype.trim
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
9.1 KiB
…minify/client.app.min.js?1111-223-03092025:1:2128
(static.revechat.com)
@babel/plugin-transform-spread
…minify/client.app.min.js?1111-223-03092025:1:90920
(static.revechat.com)
Array.prototype.find
…minify/client.app.min.js?1111-223-03092025:1:91268
(static.revechat.com)
Array.prototype.findIndex
…minify/client.app.min.js?1111-223-03092025:1:1531361
(static.revechat.com)
Array.prototype.forEach
…minify/client.app.min.js?1111-223-03092025:1:230105
(static.revechat.com)
Array.prototype.indexOf
…minify/client.app.min.js?1111-223-03092025:1:1531727
(static.revechat.com)
Object.create
…minify/client.app.min.js?1111-223-03092025:1:1532090
(static.revechat.com)
String.prototype.startsWith
…minify/client.app.min.js?1111-223-03092025:1:1531263
(static.revechat.com)
String.prototype.trim
…library/browser.js
(static.revechat.com)
0.7 KiB
…library/browser.js:1:658
(static.revechat.com)
@babel/plugin-transform-classes
…library/browser.js:1:4435
(static.revechat.com)
@babel/plugin-transform-regenerator
…library/browser.js:1:2566
(static.revechat.com)
@babel/plugin-transform-spread
…library/lottie-player.js
(static.revechat.com)
0.5 KiB
…library/lottie-player.js:1:5232
(static.revechat.com)
@babel/plugin-transform-classes
…library/lottie-player.js:1:14500
(static.revechat.com)
@babel/plugin-transform-spread
populardiagnostic.com
1st party
0.7 KiB
/assets/index-D9TpzPx-.js
(www.populardiagnostic.com)
0.5 KiB
/assets/index-D9TpzPx-.js:2:130372
(www.populardiagnostic.com)
@babel/plugin-transform-classes
/assets/index-D9TpzPx-.js:2:79153
(www.populardiagnostic.com)
@babel/plugin-transform-spread
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
0.3 KiB
/assets/index-B8iloa7z.js:67:21502
(www.populardiagnostic.com)
@babel/plugin-transform-spread
Avoid document.write()
For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of seconds. Learn how to avoid document.write().
Source
revechat.com
…scripts/new-livechat.js?175…:1:6746
(static.revechat.com)
…scripts/new-livechat.js?175…:1:6927
(static.revechat.com)
…scripts/new-livechat.js?175…:1:6612
(static.revechat.com)
Avoid enormous network payloads Total size was 4,297 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
URL
Transfer Size
populardiagnostic.com
1st party
1,846.6 KiB
/assets/4-33a2F2a_.webp
(www.populardiagnostic.com)
501.4 KiB
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
334.2 KiB
/assets/5-DVECcc1c.webp
(www.populardiagnostic.com)
224.9 KiB
/assets/6-CS5LWHS4.webp
(www.populardiagnostic.com)
218.8 KiB
/assets/3-D5xSDq2G.webp
(www.populardiagnostic.com)
167.1 KiB
/assets/2-CgtAcksK.webp
(www.populardiagnostic.com)
142.1 KiB
/assets/link-BH2Tfz_i.webp
(www.populardiagnostic.com)
130.1 KiB
/assets/11-T1pN_r_p.webp
(www.populardiagnostic.com)
128.0 KiB
revechat.com
810.1 KiB
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
673.8 KiB
…sound/cellphone_ring_tone_2.mp3
(static.revechat.com)
136.3 KiB
Avoid long main-thread tasks 7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasksTBT
URL
Start Time
Duration
revechat.com
545 ms
…minify/client.app.min.js?1111-223-03092025
(static.revechat.com)
2,729 ms
487 ms
…library/lottie-player.js
(static.revechat.com)
3,416 ms
58 ms
populardiagnostic.com
1st party
300 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
221 ms
94 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
3,759 ms
93 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
369 ms
60 ms
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
1,274 ms
53 ms
Unattributable
51 ms
Unattributable
318 ms
51 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (11)
Show Hide
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.LCPFCP
  • Avoids redirects
  • Server responds quickly (observed 258 ms)
  • Applies text compression
Optimize DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size.
Statistic
Element
Value
Total elements
670
Most children
Healthcare service 2
<div class="relative h-[300px] sm:h-[400px] md:h-[500px] lg:h-[600px] w-full">
15
DOM depth
23
<div>
15
Duplicated JavaScript
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.LCPFCP
Font display
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Forced reflow
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
INP breakdown
Start investigating with the longest subpart. Delays can be minimized. To reduce processing duration, optimize the main-thread costs, often JS.
Optimize viewport for mobile
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
head > meta
<meta name="viewport" content="width=device-width, initial-scale=1.0">
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.LCPFCP
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more about User Timing marks.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.TBT
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as passive to improve your page's scroll performance. Learn more about adopting passive event listeners.
89
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Failing Elements
Appointment
<button type="button" class="inline-block w-full p-3 shadow-2xl rounded text-gray-900 border-r border-g…">
Test Prices
<button type="button" class="inline-block w-full p-3 shadow-2xl rounded text-gray-900 border-r border-g…">
Do you need Emergency Medical Care? Call @ 10636
<h1 class="text-xl sm:text-2xl lg:text-3xl xl:text-4xl font-ubuntu font-bold mb-3 sm:…">
main.relative > section > div.w-full > div.absolute
<div class="absolute w-full h-full top-0 left-0 bg-[#00984a]/70">
main.relative > section > div.w-full > div.w-full
<div class="w-full h-full absolute top-0 left-0 bg-[#00984a]/30">
Doctors Appointment Test Prices Select Branch Select Specialization Select Day …
<div class="bg-[#ffffff]">
or 09666 787801. You can also reach us by the email: info@populardiagnostic.com
<p class="text-sm sm:text-base lg:text-lg font-medium mb-4 sm:mb-6 leading-relaxed m…">
main.relative > section > div.w-full > div.absolute
<div class="absolute w-full h-full top-0 left-0 bg-[#00984a]/70">
main.relative > section > div.w-full > div.w-full
<div class="w-full h-full absolute top-0 left-0 bg-[#00984a]/30">
Doctors Appointment Test Prices Select Branch Select Specialization Select Day …
<div class="bg-[#ffffff]">
Call Now
<a href="tel:10636" class="bg-white text-[#00984a] border rounded px-4 py-3 sm:px-6 sm:py-3 sm:m-2 ho…">
Learn More
<a class="bg-transparent border border-white text-white rounded px-4 py-3 sm:px-6 sm…" href="/hotlines">
main.relative > section > div.w-full > div.absolute
<div class="absolute w-full h-full top-0 left-0 bg-[#00984a]/70">
main.relative > section > div.w-full > div.w-full
<div class="w-full h-full absolute top-0 left-0 bg-[#00984a]/30">
Doctors Appointment Test Prices Select Branch Select Specialization Select Day …
<div class="bg-[#ffffff]">
CONTACT US
<h3 class="text-lg font-bold uppercase tracking-wider">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Head Office (Dhanmondi):
<p class="font-semibold">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
House #16, Road # 2, Dhanmondi R/A, Dhaka-1205, Bangladesh
<p class="py-2">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Phone: 09666 787801, 10636
<p class="mt-4">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
09666 787801
<a href="tel:09666787801" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
10636
<a href="tel:10636" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
View All Branch Hotlines →
<a class="inline-block transition-colors text-sm" href="/hotlines">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
E-mail: info@populardiagnostic.com
<p>
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
info@populardiagnostic.com
<a href="mailto:info@populardiagnostic.com" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
IMPORTANT LINKS
<h3 class="text-lg font-bold uppercase tracking-wider">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Popular Medical College Hospital
<a href="https://www.popular-hospital.com/" target="_blank" rel="noopener noreferrer" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Popular Pharmaceuticals
<a href="https://www.popular-pharma.com/" target="_blank" rel="noopener noreferrer" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Popular Medical College
<a href="https://www.pmch-bd.org/" target="_blank" rel="noopener noreferrer" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
QUICK LINKS
<h3 class="text-lg font-bold uppercase tracking-wider">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Our Branches
<a class="hover:underline" href="/our-branches">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Call for Appointments
<a href="http://appointment.populardiagnostic.com/appointment" target="_blank" rel="noopener noreferrer" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Find Doctors
<a class="hover:underline" href="/our-doctors">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
Complain & Advise
<a href="https://complain.populardiagnostic.com/" class="hover:underline">
CONTACT US Head Office (Dhanmondi): House #16, Road # 2, Dhanmondi R/A, Dhaka…
<footer class="w-full bg-[#00984a] text-white">
These are opportunities to improve the legibility of your content.
Names and labels
<frame> or <iframe> elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Failing Elements
body > div#reve-chat-container-div > iframe#reve-chat-widget-holder-2
<iframe id="reve-chat-widget-holder-2" src="about:blank" name="reve-chat-widget-holder-2" allow="camera *;microphone *" scrolling="no" style="z-index: 2147483645; min-width: 48px; width: 48px; position: fixed;">
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Failing Elements
div.relative > div.space-y-3 > div.relative > a.flex
<a class="flex items-center justify-end group cursor-pointer" href="/hotlines">
div.relative > div.space-y-3 > div.relative > a.flex
<a href="/patient_portal" class="flex items-center justify-end group cursor-pointer" tabindex="0">
div.relative > div.space-y-3 > div.relative > a.flex
<a href="/our-doctors" class="flex items-center justify-end group cursor-pointer" tabindex="0">
div.relative > div.space-y-3 > div.relative > a.flex
<a href="https://appointment.populardiagnostic.com/appointment" target="_blank" rel="noopener noreferrer" class="flex items-center justify-end group cursor-pointer" tabindex="0">
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Additional items to manually check (10)
Show Hide
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls focusable.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn how to decorate interactive elements with affordance hints.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about logical tab ordering.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual ordering.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn how to avoid focus traps.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn how to direct focus to new content.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more about landmark elements.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom controls and labels.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (25)
Show Hide
[aria-*] attributes match their roles
Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn how to match ARIA attributes to their roles.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when aria-hidden="true" is set on the document <body>. Learn how aria-hidden affects the document body.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
ARIA attributes are used as specified for the element's role
Some ARIA attributes are only allowed on an element under certain conditions. Learn more about conditional ARIA attributes.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an [aria-hidden="true"] element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how aria-hidden affects focusable elements.
Elements use only permitted ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly. Learn more about proper list structure.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the tabindex attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Uses ARIA roles only on compatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Deprecated ARIA roles were not used
Deprecated ARIA roles may not be processed correctly by assistive technology. Learn more about deprecated ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the alt attribute.
Not applicable (29)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more about access keys.
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
ARIA meter elements have accessible names
When a meter element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name meter elements.
ARIA progressbar elements have accessible names
When a progressbar element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label progressbar elements.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Elements with the role=text attribute do not have focusable descendents.
Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's focusable descendents will not be announced. Learn more about the role=text attribute.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.
ARIA tooltip elements have accessible names
When a tooltip element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to name tooltip elements.
ARIA treeitem elements have accessible names
When a treeitem element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about labeling treeitem elements.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more about bypass blocks.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Definition list items are wrapped in <dl> elements
Definition list items (<dt> and <dd>) must be wrapped in a parent <dl> element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn how to fix duplicate ARIA IDs.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn how to use form labels.
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly. Learn more about the lang attribute.
Input buttons have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
<input type="image"> elements have [alt] text
When an image is being used as an <input> button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
Links are distinguishable without relying on color.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to <object> elements helps screen readers convey meaning to users. Learn more about alt text for object elements.
Select elements have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the select element.
Tables have different content in the summary attribute and <caption>.
The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table mark-up helps users of screen readers. Learn more about summary and caption.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring <td> cells using the [headers] attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more about the headers attribute.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more about table headers.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the lang attribute.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
78
Best Practices
General
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Deprecation / Warning
Source
revechat.com
Unload event listeners are deprecated and will be removed.
…jquery/jquery.js:1083:10
(static.revechat.com)
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Source
Description
populardiagnostic.com
1st party
/assets/main-dcfkQSH9.jsx:1:0
(www.populardiagnostic.com)
Failed to load module script: Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of "application/x-www-form-urlencoded". Strict MIME type checking is enforced for module scripts per HTML spec.
/api/testimonials?token=UCbuv3xIy…:1:0
(api.populardiagnostic.com)
Failed to load resource: net::ERR_TIMED_OUT
revechat.com
…minify/client.app.min.js?1111-223-03092025:1:2508641
(static.revechat.com)
WebSocket connection to 'wss://chat-socket.revechat.com/s/W/ws/FjwmpaAFrpzguaYz/f/1759079896983' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
…minify/client.app.min.js?1111-223-03092025:1:2508641
(static.revechat.com)
WebSocket connection to 'wss://chat-socket.revechat.com/s/W/ws/JecerLHSO3W4LfSI/E/1759079902029' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
…minify/client.app.min.js?1111-223-03092025:1:2508641
(static.revechat.com)
WebSocket connection to 'wss://chat-socket.revechat.com/s/W/ws/Y2fTr8Yao7iYcqlw/n/1759079907043' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
URL
Map URL
populardiagnostic.com
1st party
/assets/index-B8iloa7z.js
(www.populardiagnostic.com)
Large JavaScript file is missing a source map
revechat.com
…library/dexie.js
(static.revechat.com)
…library/dexie.min.js.map
(static.revechat.com)
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
JSDelivr CDN
cdn
…@phosphor-icons/web@2.1.1
(cdn.jsdelivr.net)
/sm/9367c94….map
(cdn.jsdelivr.net)
Trust and Safety
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Description
Directive
Severity
No CSP found in enforcement mode
High
Use a strong HSTS policy
Deployment of the HSTS header significantly reduces the risk of downgrading HTTP connections and eavesdropping attacks. A rollout in stages, starting with a low max-age is recommended. Learn more about using a strong HSTS policy.
Description
Directive
Severity
No HSTS header found
High
Ensure proper origin isolation with COOP
The Cross-Origin-Opener-Policy (COOP) can be used to isolate the top-level window from other documents such as pop-ups. Learn more about deploying the COOP header.
Description
Directive
Severity
No COOP header found
High
Mitigate clickjacking with XFO or CSP
The X-Frame-Options (XFO) header or the frame-ancestors directive in the Content-Security-Policy (CSP) header control where a page can be embedded. These can mitigate clickjacking attacks by blocking some or all sites from embedding the page. Learn more about mitigating clickjacking.
Description
Severity
No frame control policy found
High
Mitigate DOM-based XSS with Trusted Types
The require-trusted-types-for directive in the Content-Security-Policy (CSP) header instructs user agents to control the data passed to DOM XSS sink functions. Learn more about mitigating DOM-based XSS with Trusted Types.
Description
Severity
No `Content-Security-Policy` header with Trusted Types directive found
High
Passed audits (11)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Avoids third-party cookies
Third-party cookies may be blocked in some contexts. Learn more about preparing for third-party cookie restrictions.
Allows users to paste into input fields
Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more about responsibly getting permission for notifications.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Has a <meta name="viewport"> tag with width or initial-scale
A <meta name="viewport"> not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.
Properly defines charset
A character encoding declaration is required. It can be done with a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Issues panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (3)
Show Hide
Redirects HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Document uses legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
75
SEO
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Content Best Practices
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Link destination
Link Text
populardiagnostic.com
1st party
/hotlines
(www.populardiagnostic.com)
Learn More
Format your HTML in a way that enables crawlers to better understand your app’s content.
Crawling and Indexing
robots.txt is not valid 43 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Line #
Content
Error
1
<!DOCTYPE html>
Syntax not understood
2
<html lang="en">
Syntax not understood
3
  <head>
Syntax not understood
4
    <meta charset="UTF-8" />
Syntax not understood
5
    <link rel="icon" type="image/svg+xml" href="/assets/logo1-61ask-p-.webp" />
Syntax not understood
6
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
Syntax not understood
8
    <!-- Performance optimization meta tags -->
Syntax not understood
9
    <meta name="format-detection" content="telephone=no" />
Syntax not understood
10
    <meta name="theme-color" content="#00984a" />
Syntax not understood
12
    <!-- Preconnect to external domains for faster loading -->
Syntax not understood
13
    <link rel="preconnect" href="https://api.populardiagnostic.com" />
Unknown directive
14
    <link rel="preconnect" href="https://fonts.googleapis.com" />
Unknown directive
15
    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
Unknown directive
16
    <link rel="preconnect" href="https://static.revechat.com" />
Unknown directive
18
    <!-- Preload critical assets -->
Syntax not understood
19
    <link rel="modulepreload" href="/assets/main-dcfkQSH9.jsx" />
Syntax not understood
20
    <link rel="preload" href="/assets/logo-D2TkWYd3.webp" as="image" type="image/webp" />
Syntax not understood
22
    <!-- Font optimization -->
Syntax not understood
23
    <link rel="preload" href="https://fonts.googleapis.com/css2?family=Ubuntu:wght@300;400;500;600;700&display=swap" as="style" />
Unknown directive
24
    <link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Ubuntu:wght@300;400;500;600;700&display=swap" media="print" onload="this.media='all'" />
Unknown directive
26
    <title>Popular Diagnostic Centre Ltd.</title>
Syntax not understood
27
    <script type="module" crossorigin src="/assets/index-B8iloa7z.js"></script>
Syntax not understood
28
    <link rel="stylesheet" crossorigin href="/assets/index-D6li_RNe.css">
Syntax not understood
29
  </head>
Syntax not understood
30
  <body>
Syntax not understood
31
    <div id="root"></div>
Syntax not understood
33
<!-- Start of REVE Chat Script - Deferred for performance -->
Syntax not understood
34
<script type='text/javascript' defer>
Syntax not understood
35
  // Defer chat loading until page is fully loaded
Syntax not understood
36
  window.addEventListener('load', function() {
Syntax not understood
37
    setTimeout(function() {
Syntax not understood
38
      window.$_REVECHAT_API || (function (d, w) {
Syntax not understood
39
        var r = $_REVECHAT_API = function (c) { r._.push(c); }; w.__revechat_account = '6395607'; w.__revechat_version = 2;
Syntax not understood
40
        r._ = []; var rc = d.createElement('script'); rc.type = 'text/javascript'; rc.async = true; rc.setAttribute('charset', 'utf-8');
Syntax not understood
41
        rc.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + 'static.revechat.com' + '/widget/scripts/new-livechat.js?' + new Date().getTime();
Unknown directive
42
        var s = d.getElementsByTagName('script')[0]; s.parentNode.insertBefore(rc, s);
Syntax not understood
43
      })(document, window);
Syntax not understood
44
    }, 2000); // Load chat after 2 seconds
Syntax not understood
45
  });
Syntax not understood
46
</script>
Syntax not understood
47
<!-- End of REVE Chat Script -->
Syntax not understood
48
  </body>
Syntax not understood
49
</html>
Syntax not understood
To appear in search results, crawlers need access to your app.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more about Structured Data.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (6)
Show Hide
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.
Links are crawlable
Search engines may use href attributes on links to crawl websites. Ensure that the href attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the alt attribute.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about hreflang.
Not applicable (1)
Show Hide
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more about canonical links.